Skip to content

Conversation

@jacobdalamb
Copy link
Contributor

@jacobdalamb jacobdalamb commented Oct 5, 2025

Changes

Updates Node v18 'retiring' notice to 'deprecated' for Vercel adapter.
Removes removeDate from 'deprecated' notice text.

Testing

n/a

Docs

n/a

@changeset-bot
Copy link

changeset-bot bot commented Oct 5, 2025

🦋 Changeset detected

Latest commit: 02c3eab

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions github-actions bot added the pkg: integration Related to any renderer integration (scope) label Oct 5, 2025
@jacobdalamb jacobdalamb changed the title chore: Remove Node v18 (retired) chore(vercel): Remove Node v18 (retired) Oct 5, 2025
@jacobdalamb jacobdalamb changed the title chore(vercel): Remove Node v18 (retired) fix(vercel): Removes Node v18 notice Oct 5, 2025
@ematipico ematipico added this to the v5.15.0 milestone Oct 16, 2025
'@astrojs/vercel': major
---

Removes deprecation notice for Node.js 18 as Vercel no longer supports it.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just checking: does this PR only remove the deprecation notice, or does it actually remove support entirely? There's a difference! 😅

Here's an example from the v3 upgrade guide of how we've typically documented removing support for a Node version. Do you want to take a shot at writing something like this @jacobdalamb ? For a major update, and breaking change, we also always include a #### What should I do? section with specific guidance.

Then, tag me in and I'll take a look at it!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it only removes the deprecation notice.
Any user still on Node.js v18 or older will get a warning and Astro will default to using Node.js v22 (default) as the runtime anyway.

@sarah11918
Copy link
Member

Also noting, I checked what we say in docs about the minimum/supported Node versions for the Vercel adapter, and I think we should be good and no docs changes are needed.

@jacobdalamb jacobdalamb changed the title fix(vercel): Removes Node v18 notice fix(vercel): Updates Node v18 notice Oct 16, 2025
Eliminates the 'removal' date property from deprecated Node.js version support and related formatting logic. This simplifies the SUPPORTED_NODE_VERSIONS structure and warning messages.
@jacobdalamb jacobdalamb closed this by deleting the head repository Oct 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pkg: integration Related to any renderer integration (scope)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants